Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfd0860581bb4067fa8e68b2c1aa850ffe9b1bbe242b5cf064a7079c4fe6b168

Tx prefix hash: 4bf98083ba2e764aba94bfbbfcb1dc4f5d3279a4e84ba58bc6a1343e939a1c81
Tx public key: 5c73119e049dfaec83fc99586279bd9d25e7a2ad84f042db31359b520ded7ff3
Timestamp: 1578645586 Timestamp [UCT]: 2020-01-10 08:39:46 Age [y:d:h:m:s]: 05:123:18:45:50
Block: 42393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1238633 RingCT/type: yes/0
Extra: 015c73119e049dfaec83fc99586279bd9d25e7a2ad84f042db31359b520ded7ff30211000000058a2ee0d9000000000000000000

1 output(s) for total of 444.165326960000 dcy

stealth address amount amount idx
00: c84b6ff125abd89b2939953cb234ef34108a946e60c0b298983df0dc0c04813d 444.165326960000 76361 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": 42403, "vin": [ { "gen": { "height": 42393 } } ], "vout": [ { "amount": 444165326960, "target": { "key": "c84b6ff125abd89b2939953cb234ef34108a946e60c0b298983df0dc0c04813d" } } ], "extra": [ 1, 92, 115, 17, 158, 4, 157, 250, 236, 131, 252, 153, 88, 98, 121, 189, 157, 37, 231, 162, 173, 132, 240, 66, 219, 49, 53, 155, 82, 13, 237, 127, 243, 2, 17, 0, 0, 0, 5, 138, 46, 224, 217, 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