Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ffdbe5f8b6e3129aaa50a02da4bf5c5bf762c61a5e028694d247cbe04c3ef15

Tx prefix hash: 6504e097e5be6a5f39a059facaf8d5cb843aa2cd3b23d3b31c0c87a6423a7924
Tx public key: f233e5cddc99f4a883c9dcf725d75e7b02d29004be63c3afa42aa57ee65dbedf
Timestamp: 1631805355 Timestamp [UCT]: 2021-09-16 15:15:55 Age [y:d:h:m:s]: 03:071:05:13:27
Block: 334985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 826651 RingCT/type: yes/0
Extra: 01f233e5cddc99f4a883c9dcf725d75e7b02d29004be63c3afa42aa57ee65dbedf02110000001d8d0de867000000000000000000

1 output(s) for total of 47.649250672000 dcy

stealth address amount amount idx
00: dae159d9719cecfb7dc7784f78639fbb270cf2f77a2b33b9a949b3a036a35ea7 47.649250672000 690664 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": 334995, "vin": [ { "gen": { "height": 334985 } } ], "vout": [ { "amount": 47649250672, "target": { "key": "dae159d9719cecfb7dc7784f78639fbb270cf2f77a2b33b9a949b3a036a35ea7" } } ], "extra": [ 1, 242, 51, 229, 205, 220, 153, 244, 168, 131, 201, 220, 247, 37, 215, 94, 123, 2, 210, 144, 4, 190, 99, 195, 175, 164, 42, 165, 126, 230, 93, 190, 223, 2, 17, 0, 0, 0, 29, 141, 13, 232, 103, 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