Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35e6fc713bc8cef89aeae694dee039f333c8319e12074e6d1dd3afdc024e4df0

Tx prefix hash: ce22b928226ff0132125c9c9fbf970e5fcad20489f7bd92c77a7f9b5c0ccd4e8
Tx public key: 5debee05104f7ebd0786a23a9ebdaa62f16cac41faa94c217ebd21fcd6644921
Timestamp: 1672806871 Timestamp [UCT]: 2023-01-04 04:34:31 Age [y:d:h:m:s]: 01:333:06:00:18
Block: 667168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499192 RingCT/type: yes/0
Extra: 015debee05104f7ebd0786a23a9ebdaa62f16cac41faa94c217ebd21fcd664492102110000000333af99f4000000000000000000

1 output(s) for total of 3.779161249000 dcy

stealth address amount amount idx
00: f4a5c0f3ea22eb4eda85d033a495f1de4037d79249083a2e7eec6582cb94fc34 3.779161249000 1108333 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": 667178, "vin": [ { "gen": { "height": 667168 } } ], "vout": [ { "amount": 3779161249, "target": { "key": "f4a5c0f3ea22eb4eda85d033a495f1de4037d79249083a2e7eec6582cb94fc34" } } ], "extra": [ 1, 93, 235, 238, 5, 16, 79, 126, 189, 7, 134, 162, 58, 158, 189, 170, 98, 241, 108, 172, 65, 250, 169, 76, 33, 126, 189, 33, 252, 214, 100, 73, 33, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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