Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ee533f142c7c2cac3562c13f0f183634336d6783723d39133e1054b1b0cc4053

Tx prefix hash: 4310a46770879fd49edb48c1a0d2d9b763fb97b23384f76a84ab8e41eccc1eae
Tx public key: 5b8e14d575b5cb07520847e3dbac4da0ddf7968c345b6d6c79450ab8470a2ec5
Timestamp: 1723669894 Timestamp [UCT]: 2024-08-14 21:11:34 Age [y:d:h:m:s]: 00:288:07:56:55
Block: 1087974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205998 RingCT/type: yes/0
Extra: 015b8e14d575b5cb07520847e3dbac4da0ddf7968c345b6d6c79450ab8470a2ec502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b4dff555b813e00b09ce85dcbe875d3f51bc75e641feb50009be38e7b99c434 0.600000000000 1562585 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1087984, "vin": [ { "gen": { "height": 1087974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b4dff555b813e00b09ce85dcbe875d3f51bc75e641feb50009be38e7b99c434" } } ], "extra": [ 1, 91, 142, 20, 213, 117, 181, 203, 7, 82, 8, 71, 227, 219, 172, 77, 160, 221, 247, 150, 140, 52, 91, 109, 108, 121, 69, 10, 184, 71, 10, 46, 197, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8