Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f2734e6f1bd52308c13b2313d6cc50023b6f6a778b239eb695b9ad7a5288f1b

Tx prefix hash: deb45a28aa26db01ffe7f0f4e64c86c15822b8e4b24e0187675c72a4a183a5ee
Tx public key: 175aa6641696c6cf4487fb75ad6ea16758f3b61f02463ebb3cef1557e4566b9c
Timestamp: 1581970965 Timestamp [UCT]: 2020-02-17 20:22:45 Age [y:d:h:m:s]: 04:319:19:50:51
Block: 67028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120954 RingCT/type: yes/0
Extra: 01175aa6641696c6cf4487fb75ad6ea16758f3b61f02463ebb3cef1557e4566b9c0211000000194ac5aa02000000000000000000

1 output(s) for total of 368.052031654000 dcy

stealth address amount amount idx
00: 6edcde9865c449e4bb49667a8fca61fbf928d1fec712cea4cfa34d79786740cc 368.052031654000 123448 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": 67038, "vin": [ { "gen": { "height": 67028 } } ], "vout": [ { "amount": 368052031654, "target": { "key": "6edcde9865c449e4bb49667a8fca61fbf928d1fec712cea4cfa34d79786740cc" } } ], "extra": [ 1, 23, 90, 166, 100, 22, 150, 198, 207, 68, 135, 251, 117, 173, 110, 161, 103, 88, 243, 182, 31, 2, 70, 62, 187, 60, 239, 21, 87, 228, 86, 107, 156, 2, 17, 0, 0, 0, 25, 74, 197, 170, 2, 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