Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d56114f295425f7c467608f47e23473d71476e863c04f928f517e18a4499fa88

Tx prefix hash: bccb5ad8a982c59e0e01158cf68eb7f4c953deb735d415e4ae04dd4a8ae526dc
Tx public key: 3c592dcb9ec6212fc60c8e4b8cba8db926e99695ae8e919cfae8571438f14a36
Timestamp: 1636695622 Timestamp [UCT]: 2021-11-12 05:40:22 Age [y:d:h:m:s]: 03:013:12:06:58
Block: 372591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 788250 RingCT/type: yes/0
Extra: 013c592dcb9ec6212fc60c8e4b8cba8db926e99695ae8e919cfae8571438f14a3602110000000742b3953e000000000000000000

1 output(s) for total of 35.764465394000 dcy

stealth address amount amount idx
00: fdd6fd954a4df6832eec63ac3ec9a6f3a1a5d77e62cf41d5be7c3393499f0f9a 35.764465394000 754723 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": 372601, "vin": [ { "gen": { "height": 372591 } } ], "vout": [ { "amount": 35764465394, "target": { "key": "fdd6fd954a4df6832eec63ac3ec9a6f3a1a5d77e62cf41d5be7c3393499f0f9a" } } ], "extra": [ 1, 60, 89, 45, 203, 158, 198, 33, 47, 198, 12, 142, 75, 140, 186, 141, 185, 38, 233, 150, 149, 174, 142, 145, 156, 250, 232, 87, 20, 56, 241, 74, 54, 2, 17, 0, 0, 0, 7, 66, 179, 149, 62, 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