Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 734518109fe73d80bfbd9fa2e288e0b665f0505a4dc9a0c91815d1519d41cdcd

Tx prefix hash: 0c25cdb683f166011a5c0cb764d37f09dce002bd553d0aae41f43e412ff32493
Tx public key: 4d21a03ec342be6986f27561b9bd6826d2ad8c48a03a22a4f929f123a26336a0
Timestamp: 1710820801 Timestamp [UCT]: 2024-03-19 04:00:01 Age [y:d:h:m:s]: 00:237:05:55:46
Block: 981471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169823 RingCT/type: yes/0
Extra: 014d21a03ec342be6986f27561b9bd6826d2ad8c48a03a22a4f929f123a26336a00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a43eb4aae9c898d5209516712b487560c941c5686a49956be5ea0f4a3f116f1a 0.600000000000 1441568 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": 981481, "vin": [ { "gen": { "height": 981471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a43eb4aae9c898d5209516712b487560c941c5686a49956be5ea0f4a3f116f1a" } } ], "extra": [ 1, 77, 33, 160, 62, 195, 66, 190, 105, 134, 242, 117, 97, 185, 189, 104, 38, 210, 173, 140, 72, 160, 58, 34, 164, 249, 41, 241, 35, 162, 99, 54, 160, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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