Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4c48e1ff281aa66e97fe074c1e5361f97a38d34e0ee04bfe5048cb9facd8d8

Tx prefix hash: b19f746779d17703522d634be742725c71c07b110c4a8717a40dc3f88e4fea5c
Tx public key: 18d1ae92271ddf7ac912420abed8a4c3293bd693752f858379edee50dca2b230
Timestamp: 1673052602 Timestamp [UCT]: 2023-01-07 00:50:02 Age [y:d:h:m:s]: 02:107:18:06:46
Block: 669190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598717 RingCT/type: yes/0
Extra: 0118d1ae92271ddf7ac912420abed8a4c3293bd693752f858379edee50dca2b23002110000000252542ceb000000000000000000

1 output(s) for total of 3.721308667000 dcy

stealth address amount amount idx
00: 1b97694b60e152c94c57705655e16e75bbfd599c6aa642ab6d3ea0f2c4a4c822 3.721308667000 1110493 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": 669200, "vin": [ { "gen": { "height": 669190 } } ], "vout": [ { "amount": 3721308667, "target": { "key": "1b97694b60e152c94c57705655e16e75bbfd599c6aa642ab6d3ea0f2c4a4c822" } } ], "extra": [ 1, 24, 209, 174, 146, 39, 29, 223, 122, 201, 18, 66, 10, 190, 216, 164, 195, 41, 59, 214, 147, 117, 47, 133, 131, 121, 237, 238, 80, 220, 162, 178, 48, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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