Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ccec49899e5f0bfddd09c3a4c13828292d9fb1170949611f0f6952a81da0c82

Tx prefix hash: 815ebc6336b5e78725f5f9450a324d69700888371d05f409b955ecddac6fc7fc
Tx public key: b2dedf6a7bb25f92cbf98db8df2d00934ef2f85d4ed3eba4a957bede925b4f41
Timestamp: 1698520409 Timestamp [UCT]: 2023-10-28 19:13:29 Age [y:d:h:m:s]: 01:218:19:50:47
Block: 879686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417448 RingCT/type: yes/0
Extra: 01b2dedf6a7bb25f92cbf98db8df2d00934ef2f85d4ed3eba4a957bede925b4f4102110000000875e3f0e9000000000000000000

1 output(s) for total of 0.746862983000 dcy

stealth address amount amount idx
00: 8c7769e67fccbd4c0e2096d5b8c2de7cf53fdde11d8422b23de2ba580c3113bd 0.746862983000 1335220 of 0

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": 879696, "vin": [ { "gen": { "height": 879686 } } ], "vout": [ { "amount": 746862983, "target": { "key": "8c7769e67fccbd4c0e2096d5b8c2de7cf53fdde11d8422b23de2ba580c3113bd" } } ], "extra": [ 1, 178, 222, 223, 106, 123, 178, 95, 146, 203, 249, 141, 184, 223, 45, 0, 147, 78, 242, 248, 93, 78, 211, 235, 164, 169, 87, 190, 222, 146, 91, 79, 65, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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