Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a86953cf0399cf64d59de7bcb4e0839c7b2c8ca196eb6d7c64c8d01ad10262aa

Tx prefix hash: e6439e525215b35d49675a2a2ec9808d3656f6b5217550deb866e70cf86e0055
Tx public key: 67fc1c05dfd0cd77b50cee62948f3d903e82d5a3418f6db6064f85b17e988290
Timestamp: 1704518573 Timestamp [UCT]: 2024-01-06 05:22:53 Age [y:d:h:m:s]: 01:314:00:33:57
Block: 929182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483283 RingCT/type: yes/0
Extra: 0167fc1c05dfd0cd77b50cee62948f3d903e82d5a3418f6db6064f85b17e9882900211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc35d0c14d5cd912fc282e2f3a73366ed84792ad942b0b2a35a22df85ac7449e 0.600000000000 1387050 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": 929192, "vin": [ { "gen": { "height": 929182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc35d0c14d5cd912fc282e2f3a73366ed84792ad942b0b2a35a22df85ac7449e" } } ], "extra": [ 1, 103, 252, 28, 5, 223, 208, 205, 119, 181, 12, 238, 98, 148, 143, 61, 144, 62, 130, 213, 163, 65, 143, 109, 182, 6, 79, 133, 177, 126, 152, 130, 144, 2, 17, 0, 0, 0, 4, 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