Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33c379bddca78c93dfd5f3905a3c72a77641bd038725f9b4319832885dcff60a

Tx prefix hash: 57e08d201318ad4c9d5c0945aae59b2ce3283ec2b6e4230e9577e69d6ea7bd21
Tx public key: a4171068b0e9b15a6e80dadab6e0a53f7c8ad0c10c4cd663878049f3ef1a8eaa
Timestamp: 1719726731 Timestamp [UCT]: 2024-06-30 05:52:11 Age [y:d:h:m:s]: 00:333:21:49:57
Block: 1055278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238650 RingCT/type: yes/0
Extra: 01a4171068b0e9b15a6e80dadab6e0a53f7c8ad0c10c4cd663878049f3ef1a8eaa0211000000030cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c579c4da55dc4c264e47b996899cdf1c1b7c5abad99ca6c6e6fc75d087ca00e0 0.600000000000 1525675 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": 1055288, "vin": [ { "gen": { "height": 1055278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c579c4da55dc4c264e47b996899cdf1c1b7c5abad99ca6c6e6fc75d087ca00e0" } } ], "extra": [ 1, 164, 23, 16, 104, 176, 233, 177, 90, 110, 128, 218, 218, 182, 224, 165, 63, 124, 138, 208, 193, 12, 76, 214, 99, 135, 128, 73, 243, 239, 26, 142, 170, 2, 17, 0, 0, 0, 3, 12, 206, 6, 54, 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