Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f079d84dea472f2ce270e679783d1e632718c0d3ce6c4f10c5371e82febec51b

Tx prefix hash: dfd265d0e662ef0ea3740d2e869856da346231b72917a0c803ebedd69ae55b00
Tx public key: 779bcd6e03b3180cff6ef5492394f39a36b7fe5734a5b821d0379ca5eff9327b
Timestamp: 1704490574 Timestamp [UCT]: 2024-01-05 21:36:14 Age [y:d:h:m:s]: 01:130:05:54:22
Block: 928953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354229 RingCT/type: yes/0
Extra: 01779bcd6e03b3180cff6ef5492394f39a36b7fe5734a5b821d0379ca5eff9327b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8d184746287c9a03af1e1fc18f0898e1d5be277cdf80e3880828c6f1433c5e2 0.600000000000 1386819 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": 928963, "vin": [ { "gen": { "height": 928953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8d184746287c9a03af1e1fc18f0898e1d5be277cdf80e3880828c6f1433c5e2" } } ], "extra": [ 1, 119, 155, 205, 110, 3, 179, 24, 12, 255, 110, 245, 73, 35, 148, 243, 154, 54, 183, 254, 87, 52, 165, 184, 33, 208, 55, 156, 165, 239, 249, 50, 123, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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