Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa66289bc80f607b91abcaecc24b37438dea9155ea11286333b637e4eb8d8000

Tx prefix hash: 381af9d73d85bfe7ee7ae1423f2cf3b97aabb55b0c9c70046f54d320042e3d68
Tx public key: 450b6d26bf0140471c095dc2ba4e1cbd4909bc2c81e6f03ab75ef801cd9e9ee0
Timestamp: 1739280209 Timestamp [UCT]: 2025-02-11 13:23:29 Age [y:d:h:m:s]: 00:281:07:06:54
Block: 1216959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198803 RingCT/type: yes/0
Extra: 01450b6d26bf0140471c095dc2ba4e1cbd4909bc2c81e6f03ab75ef801cd9e9ee0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff9f9af69d5541aca3d7ead7f3fe33e8f1fb350a057d930bbfb8551abc34f01f 0.600000000000 1703768 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": 1216969, "vin": [ { "gen": { "height": 1216959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff9f9af69d5541aca3d7ead7f3fe33e8f1fb350a057d930bbfb8551abc34f01f" } } ], "extra": [ 1, 69, 11, 109, 38, 191, 1, 64, 71, 28, 9, 93, 194, 186, 78, 28, 189, 73, 9, 188, 44, 129, 230, 240, 58, 183, 94, 248, 1, 205, 158, 158, 224, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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