Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e38c36008cdc2145136d65d7c780940ea45d3101f27cac9ecbe60111b4d3486

Tx prefix hash: 5a7bb72daee03b2af69f730708af51839b21d697b7471bd0d9895892bc6b4a5d
Tx public key: 8cda18df6ba62e5c6e4d23a0b0b5d258ccda3b3862b17b4af50352eed9f2b7da
Timestamp: 1704561082 Timestamp [UCT]: 2024-01-06 17:11:22 Age [y:d:h:m:s]: 02:002:19:55:11
Block: 929546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521806 RingCT/type: yes/0
Extra: 018cda18df6ba62e5c6e4d23a0b0b5d258ccda3b3862b17b4af50352eed9f2b7da02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9a1f38540a1f8a6a0c3b91d37e43a99ca9decdae79870bb7702b3692f761c29 0.600000000000 1387422 of 15

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": 929556, "vin": [ { "gen": { "height": 929546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9a1f38540a1f8a6a0c3b91d37e43a99ca9decdae79870bb7702b3692f761c29" } } ], "extra": [ 1, 140, 218, 24, 223, 107, 166, 46, 92, 110, 77, 35, 160, 176, 181, 210, 88, 204, 218, 59, 56, 98, 177, 123, 74, 245, 3, 82, 238, 217, 242, 183, 218, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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