Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88de769462bf180047c5d512ce7247aa884498ffc8e95511b20470b530ee16e3

Tx prefix hash: 72df66d9be002c3fc0a25e1e56ec8fc73f5fb7854a969b36f72ef19040dbdd71
Tx public key: 75f2fec543d0dca0aeaa9655afc0b048dd62cec5598ae4891ae70e3b705ab3af
Timestamp: 1734920632 Timestamp [UCT]: 2024-12-23 02:23:52 Age [y:d:h:m:s]: 00:177:14:52:05
Block: 1181171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126622 RingCT/type: yes/0
Extra: 0175f2fec543d0dca0aeaa9655afc0b048dd62cec5598ae4891ae70e3b705ab3af021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb12a8cdac9e5ace37aaeab670afc861c1e429ef6f7e40c8b4f4c5363d214111 0.600000000000 1667588 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": 1181181, "vin": [ { "gen": { "height": 1181171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb12a8cdac9e5ace37aaeab670afc861c1e429ef6f7e40c8b4f4c5363d214111" } } ], "extra": [ 1, 117, 242, 254, 197, 67, 208, 220, 160, 174, 170, 150, 85, 175, 192, 176, 72, 221, 98, 206, 197, 89, 138, 228, 137, 26, 231, 14, 59, 112, 90, 179, 175, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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