Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bd4083caa48187fd780a048fecf92a265e18333f8494a5bdc37f4a6f67c6c78

Tx prefix hash: 153b832d9959ce6c0ff4bd3162405f83bfc13c14b12c5a03ae9aae08999beb83
Tx public key: 83cd0a724f312fd8c780f4a1c370a4670b18e5321e1b0f1eb8059dcfa0a184ae
Timestamp: 1725401786 Timestamp [UCT]: 2024-09-03 22:16:26 Age [y:d:h:m:s]: 00:276:09:54:37
Block: 1102346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197438 RingCT/type: yes/0
Extra: 0183cd0a724f312fd8c780f4a1c370a4670b18e5321e1b0f1eb8059dcfa0a184ae02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 647ff9fae1d4a1d0753244611fc6cdfb5aa87427c6e8db5555929a8c0e65952a 0.600000000000 1578745 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": 1102356, "vin": [ { "gen": { "height": 1102346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "647ff9fae1d4a1d0753244611fc6cdfb5aa87427c6e8db5555929a8c0e65952a" } } ], "extra": [ 1, 131, 205, 10, 114, 79, 49, 47, 216, 199, 128, 244, 161, 195, 112, 164, 103, 11, 24, 229, 50, 30, 27, 15, 30, 184, 5, 157, 207, 160, 161, 132, 174, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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