Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e38e16cd20436686fe424f548dc1ac676ddfa64d4442a057899a8d058d376bf1

Tx prefix hash: f11e9589c17ec7d0c775f4fafc8b8eef03c5a8fa2fd4a73dbed6feb87cdf50f3
Tx public key: d2ba5af8290314f1763d03c83563bb2b7bcae481656966bcf79d17e2a5bad057
Timestamp: 1732608920 Timestamp [UCT]: 2024-11-26 08:15:20 Age [y:d:h:m:s]: 00:032:02:25:50
Block: 1161990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22968 RingCT/type: yes/0
Extra: 01d2ba5af8290314f1763d03c83563bb2b7bcae481656966bcf79d17e2a5bad057021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa7b22e392f5d85fcd67f758d56a356f6b5683d647a8c8f526710571ad83d1a8 0.600000000000 1647645 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": 1162000, "vin": [ { "gen": { "height": 1161990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa7b22e392f5d85fcd67f758d56a356f6b5683d647a8c8f526710571ad83d1a8" } } ], "extra": [ 1, 210, 186, 90, 248, 41, 3, 20, 241, 118, 61, 3, 200, 53, 99, 187, 43, 123, 202, 228, 129, 101, 105, 102, 188, 247, 157, 23, 226, 165, 186, 208, 87, 2, 17, 0, 0, 0, 2, 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