Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d83f0f1a73c733f50f63c892e6c2823ac8b44dba40fbdc9aaec2b80605461220

Tx prefix hash: abd91b225075d7284efede051c5aac37d4e8d9c3a7a37015e6bdb5c63bd9c3c2
Tx public key: 439ae51d8085c338d58056a8c968d4528437f6f8fd00f90b96965711499194a4
Timestamp: 1677638323 Timestamp [UCT]: 2023-03-01 02:38:43 Age [y:d:h:m:s]: 02:044:03:05:42
Block: 707236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 553120 RingCT/type: yes/0
Extra: 01439ae51d8085c338d58056a8c968d4528437f6f8fd00f90b96965711499194a402110000000183600029000000000000000000

1 output(s) for total of 2.783770621000 dcy

stealth address amount amount idx
00: 08c188909cf3be9c378e8bda575ccf32a646a894665d66ef0b04655e111ca293 2.783770621000 1151033 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": 707246, "vin": [ { "gen": { "height": 707236 } } ], "vout": [ { "amount": 2783770621, "target": { "key": "08c188909cf3be9c378e8bda575ccf32a646a894665d66ef0b04655e111ca293" } } ], "extra": [ 1, 67, 154, 229, 29, 128, 133, 195, 56, 213, 128, 86, 168, 201, 104, 212, 82, 132, 55, 246, 248, 253, 0, 249, 11, 150, 150, 87, 17, 73, 145, 148, 164, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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