Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be5eb1c1d10a6c72019bc5f082a1c995e7ffb80a0845b56abb0ea4afaa8716d

Tx prefix hash: dd9e7beb8d10c3c88d074c1104bb7bc72d9290a84c6b5d0813de00d99871f395
Tx public key: b1f8e4f48dd3a9db409c4682f111013a83a2080415faeb51a16f12ee4b75adc3
Timestamp: 1657313917 Timestamp [UCT]: 2022-07-08 20:58:37 Age [y:d:h:m:s]: 03:115:15:32:08
Block: 539561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 862368 RingCT/type: yes/0
Extra: 01b1f8e4f48dd3a9db409c4682f111013a83a2080415faeb51a16f12ee4b75adc3021100000008d3fcec30000000000000000000

1 output(s) for total of 10.005329778000 dcy

stealth address amount amount idx
00: c5fb7cb30c2ba8eb7ef3f692f76accc22e6aa144d8185af8187a4f7f50165d44 10.005329778000 969682 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": 539571, "vin": [ { "gen": { "height": 539561 } } ], "vout": [ { "amount": 10005329778, "target": { "key": "c5fb7cb30c2ba8eb7ef3f692f76accc22e6aa144d8185af8187a4f7f50165d44" } } ], "extra": [ 1, 177, 248, 228, 244, 141, 211, 169, 219, 64, 156, 70, 130, 241, 17, 1, 58, 131, 162, 8, 4, 21, 250, 235, 81, 161, 111, 18, 238, 75, 117, 173, 195, 2, 17, 0, 0, 0, 8, 211, 252, 236, 48, 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