Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 890d36b3efa0e2e994cdf292a343714c2da69c0720cbda0379d2cf88083ce498

Tx prefix hash: 2906c8783555b5ccddc24f313d73c2203cfcfd3fb077a8797122906ddfed2b1d
Tx public key: fbb10e6866913dc8e3e9dcb3006b4747508fcd8fd9a5c3d6d9a06be1066169b0
Timestamp: 1674024524 Timestamp [UCT]: 2023-01-18 06:48:44 Age [y:d:h:m:s]: 02:131:19:57:03
Block: 677255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 615930 RingCT/type: yes/0
Extra: 01fbb10e6866913dc8e3e9dcb3006b4747508fcd8fd9a5c3d6d9a06be1066169b00211000000038b7b6602000000000000000000

1 output(s) for total of 3.499234034000 dcy

stealth address amount amount idx
00: f671b4bb32e390fd575df53dd6f399b9cffa96b0a877d6f8617c1084e99313b0 3.499234034000 1119024 of 0

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": 677265, "vin": [ { "gen": { "height": 677255 } } ], "vout": [ { "amount": 3499234034, "target": { "key": "f671b4bb32e390fd575df53dd6f399b9cffa96b0a877d6f8617c1084e99313b0" } } ], "extra": [ 1, 251, 177, 14, 104, 102, 145, 61, 200, 227, 233, 220, 179, 0, 107, 71, 71, 80, 143, 205, 143, 217, 165, 195, 214, 217, 160, 107, 225, 6, 97, 105, 176, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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