Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21ae7e01a4286f0e1edff5371b8171e720d10f89d25cf9b3769b672344481166

Tx prefix hash: e27875a06881cea9d51af6d3805499e14894401eee37becaea843328a5ead55f
Tx public key: bd4fd5c4b2602b4daffcd01ee2b817ddd670971e7d31a1720dd897de7f4e062b
Timestamp: 1721017412 Timestamp [UCT]: 2024-07-15 04:23:32 Age [y:d:h:m:s]: 00:263:11:12:20
Block: 1066003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188218 RingCT/type: yes/0
Extra: 01bd4fd5c4b2602b4daffcd01ee2b817ddd670971e7d31a1720dd897de7f4e062b02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba6bf683e7cb6e13e6d207f9ab6972065b24f3faa62dfe4aabd38bc88b4aa12f 0.600000000000 1536574 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": 1066013, "vin": [ { "gen": { "height": 1066003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba6bf683e7cb6e13e6d207f9ab6972065b24f3faa62dfe4aabd38bc88b4aa12f" } } ], "extra": [ 1, 189, 79, 213, 196, 178, 96, 43, 77, 175, 252, 208, 30, 226, 184, 23, 221, 214, 112, 151, 30, 125, 49, 161, 114, 13, 216, 151, 222, 127, 78, 6, 43, 2, 17, 0, 0, 0, 3, 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