Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4d903ef97b201da23aeb6575084ccc26dd99004d9a15f311a9d1caf04db3d63

Tx prefix hash: 8476f1b4cdd9ba5ae1b3493570d4e8c26147deacd6a1caf75a7c4d3fb7af2b5a
Tx public key: b1c3a17b185be941345531309297a521ef1a78890ae8e326ef5f66e0d4c06e88
Timestamp: 1685916824 Timestamp [UCT]: 2023-06-04 22:13:44 Age [y:d:h:m:s]: 01:164:10:45:11
Block: 775237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378904 RingCT/type: yes/0
Extra: 01b1c3a17b185be941345531309297a521ef1a78890ae8e326ef5f66e0d4c06e88021100000004faf35c9c000000000000000000

1 output(s) for total of 1.656983443000 dcy

stealth address amount amount idx
00: a4142c1d0c15495f5a9013ecf45ad7e1f0e934ed6a56eeaa40378920e0171a08 1.656983443000 1224740 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": 775247, "vin": [ { "gen": { "height": 775237 } } ], "vout": [ { "amount": 1656983443, "target": { "key": "a4142c1d0c15495f5a9013ecf45ad7e1f0e934ed6a56eeaa40378920e0171a08" } } ], "extra": [ 1, 177, 195, 161, 123, 24, 91, 233, 65, 52, 85, 49, 48, 146, 151, 165, 33, 239, 26, 120, 137, 10, 232, 227, 38, 239, 95, 102, 224, 212, 192, 110, 136, 2, 17, 0, 0, 0, 4, 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