Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbda6cc7ceec4ea8507d2654c0ee459967e4ff9e93956051d512cc101dfed758

Tx prefix hash: 5aeb0273d263fe46019c66b766dffa9efc7000b6b35d891a1e860a40396fb7bd
Tx public key: 1855ae475f5ea827bcc32482842a5f52e7ffc18565bf3548143a3a226f085606
Timestamp: 1582973672 Timestamp [UCT]: 2020-02-29 10:54:32 Age [y:d:h:m:s]: 04:302:16:45:39
Block: 73957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110072 RingCT/type: yes/0
Extra: 011855ae475f5ea827bcc32482842a5f52e7ffc18565bf3548143a3a226f0856060211000001ee026b59f3000000000000000000

1 output(s) for total of 349.100569094000 dcy

stealth address amount amount idx
00: f4c3113198ecc1225fdbd588db5ad3417d574b4babed56d08176cc03679f73a4 349.100569094000 136683 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": 73967, "vin": [ { "gen": { "height": 73957 } } ], "vout": [ { "amount": 349100569094, "target": { "key": "f4c3113198ecc1225fdbd588db5ad3417d574b4babed56d08176cc03679f73a4" } } ], "extra": [ 1, 24, 85, 174, 71, 95, 94, 168, 39, 188, 195, 36, 130, 132, 42, 95, 82, 231, 255, 193, 133, 101, 191, 53, 72, 20, 58, 58, 34, 111, 8, 86, 6, 2, 17, 0, 0, 1, 238, 2, 107, 89, 243, 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