Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4695129944004db6f64faa7dc4ae57cca4494850f5f7de1ff8ce8a321d00695

Tx prefix hash: d08be85b9e41dfbd9dcd364f8be158240f9c4ebe86d272e990668a2ebd499916
Tx public key: 5aaa9d925b460f1a1ed43b8d49bcf530f1fbc3de0df435b42f9a12c91584d14b
Timestamp: 1577768405 Timestamp [UCT]: 2019-12-31 05:00:05 Age [y:d:h:m:s]: 05:065:07:23:28
Block: 35477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196471 RingCT/type: yes/0
Extra: 015aaa9d925b460f1a1ed43b8d49bcf530f1fbc3de0df435b42f9a12c91584d14b0211000000084943cd9f000000000000000000

1 output(s) for total of 468.220933033000 dcy

stealth address amount amount idx
00: eac57518c046abf82cfc75aabdc1a0aab07aa41eee591c9c519c42c0873fa77e 468.220933033000 59856 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": 35487, "vin": [ { "gen": { "height": 35477 } } ], "vout": [ { "amount": 468220933033, "target": { "key": "eac57518c046abf82cfc75aabdc1a0aab07aa41eee591c9c519c42c0873fa77e" } } ], "extra": [ 1, 90, 170, 157, 146, 91, 70, 15, 26, 30, 212, 59, 141, 73, 188, 245, 48, 241, 251, 195, 222, 13, 244, 53, 180, 47, 154, 18, 201, 21, 132, 209, 75, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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