Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bfabbdf6365c6c4e1db1276cb1a5716940c776246449a1030d4c9aae84e3e44

Tx prefix hash: cc67b915b487a31488317f97ccba1ab918e5292eac8c5c1a20a697f6b5868042
Tx public key: ed5ebfae785032af5a6ad4d764e3eec64cda5f791b0aa0a6cce15a635a2f81f2
Timestamp: 1705364776 Timestamp [UCT]: 2024-01-16 00:26:16 Age [y:d:h:m:s]: 01:079:09:14:45
Block: 936202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317843 RingCT/type: yes/0
Extra: 01ed5ebfae785032af5a6ad4d764e3eec64cda5f791b0aa0a6cce15a635a2f81f202110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5f2cbadddd9d051ea670cba8eac589f8774fa566939b3bf6e1ef44f0d1f56d4 0.600000000000 1394226 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": 936212, "vin": [ { "gen": { "height": 936202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5f2cbadddd9d051ea670cba8eac589f8774fa566939b3bf6e1ef44f0d1f56d4" } } ], "extra": [ 1, 237, 94, 191, 174, 120, 80, 50, 175, 90, 106, 212, 215, 100, 227, 238, 198, 76, 218, 95, 121, 27, 10, 160, 166, 204, 225, 90, 99, 90, 47, 129, 242, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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