Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a50d92f4ed3d0f1f40be5e466cf250f1803be89b8f8e2ff0a7de3af41a3e833

Tx prefix hash: 7bc5e5f5660d9e98f6267ffa073e923fc56b42a862f2d8e9f58bb3d9ef8651e7
Tx public key: 6e2e1841595fed3aadd49852036602f3863c73b542dbfac693e84906c779451f
Timestamp: 1733865353 Timestamp [UCT]: 2024-12-10 21:15:53 Age [y:d:h:m:s]: 00:100:02:54:53
Block: 1172407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71356 RingCT/type: yes/0
Extra: 016e2e1841595fed3aadd49852036602f3863c73b542dbfac693e84906c779451f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 382eafda31a78a75b7f0abe3c1931b048fd6685e05f5a973a654e7aea3a51405 0.600000000000 1658294 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": 1172417, "vin": [ { "gen": { "height": 1172407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "382eafda31a78a75b7f0abe3c1931b048fd6685e05f5a973a654e7aea3a51405" } } ], "extra": [ 1, 110, 46, 24, 65, 89, 95, 237, 58, 173, 212, 152, 82, 3, 102, 2, 243, 134, 60, 115, 181, 66, 219, 250, 198, 147, 232, 73, 6, 199, 121, 69, 31, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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