Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 448e5ca0103006958e49caa2985be4cb6d6e25306dd661467af1d000afd753cf

Tx prefix hash: b4d8aeee24c21a3d875de888bf7a420fd0c78719439b06c90db6e776dd0081db
Tx public key: e9b15ab716f1b3b248d29f63094009ef98f4ac77e407a1d16bbb762436c46e19
Timestamp: 1714198783 Timestamp [UCT]: 2024-04-27 06:19:43 Age [y:d:h:m:s]: 01:007:00:00:57
Block: 1009452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265947 RingCT/type: yes/0
Extra: 01e9b15ab716f1b3b248d29f63094009ef98f4ac77e407a1d16bbb762436c46e190211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d28c6da3d618d5faddd471422cc3b1533f79cd6cd515fb0b9a2bc555b82e331 0.600000000000 1471126 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": 1009462, "vin": [ { "gen": { "height": 1009452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d28c6da3d618d5faddd471422cc3b1533f79cd6cd515fb0b9a2bc555b82e331" } } ], "extra": [ 1, 233, 177, 90, 183, 22, 241, 179, 178, 72, 210, 159, 99, 9, 64, 9, 239, 152, 244, 172, 119, 228, 7, 161, 209, 107, 187, 118, 36, 54, 196, 110, 25, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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