Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c1221038cd9cec2d37b1470c35552eabfeecbaae860b3b4f4ccb8bb48200767

Tx prefix hash: 834fec70d0cfa161aa6e7df1a584b68548c7a9ec04ad52f3c4d34f6845b7a24a
Tx public key: 3049476c04d46a39261fed89a7d1f25a6179e9de3d15a87df7c916afbb479658
Timestamp: 1717882913 Timestamp [UCT]: 2024-06-08 21:41:53 Age [y:d:h:m:s]: 00:342:17:48:55
Block: 1040006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244967 RingCT/type: yes/0
Extra: 013049476c04d46a39261fed89a7d1f25a6179e9de3d15a87df7c916afbb4796580211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffd56974d282864c44a605da034d9dd13eb4f9cd2390fc7fad6849ac78f6d556 0.600000000000 1508661 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": 1040016, "vin": [ { "gen": { "height": 1040006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffd56974d282864c44a605da034d9dd13eb4f9cd2390fc7fad6849ac78f6d556" } } ], "extra": [ 1, 48, 73, 71, 108, 4, 212, 106, 57, 38, 31, 237, 137, 167, 209, 242, 90, 97, 121, 233, 222, 61, 21, 168, 125, 247, 201, 22, 175, 187, 71, 150, 88, 2, 17, 0, 0, 0, 8, 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