Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd0d3ac1700435f8b9b5906e19f107ead2aa07d38254a00aee00efecc69aa37c

Tx prefix hash: 3f757cd496b3ab2a2bbe052de13b2295b1232c37f8330c8067b610396d2bae90
Tx public key: a62fd5f0dbcf5e55420af5fcbe0bb5bf4868910af8a462c3eee5364e6f2585bf
Timestamp: 1701828679 Timestamp [UCT]: 2023-12-06 02:11:19 Age [y:d:h:m:s]: 01:120:15:08:36
Block: 906907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347358 RingCT/type: yes/0
Extra: 01a62fd5f0dbcf5e55420af5fcbe0bb5bf4868910af8a462c3eee5364e6f2585bf021100000003faf35c9c000000000000000000

1 output(s) for total of 0.606793063000 dcy

stealth address amount amount idx
00: 132559e93c970e18140abdd3294a06812fa1478d91797499924cb53254395d14 0.606793063000 1363868 of 0

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": 906917, "vin": [ { "gen": { "height": 906907 } } ], "vout": [ { "amount": 606793063, "target": { "key": "132559e93c970e18140abdd3294a06812fa1478d91797499924cb53254395d14" } } ], "extra": [ 1, 166, 47, 213, 240, 219, 207, 94, 85, 66, 10, 245, 252, 190, 11, 181, 191, 72, 104, 145, 10, 248, 164, 98, 195, 238, 229, 54, 78, 111, 37, 133, 191, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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