Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 951fb9215ff95990104487f02a202f4f3da2e97cabbb5e2bc45413a8aa4fe78b

Tx prefix hash: d64340f2cf15884962d8b01c6ac748aa7f4ade3f15fbf8e55dcd7db2e99fdf8b
Tx public key: 9bc1530781957839ae4313af4a742a3d7d9de0628beea3fe10762192df5d750c
Timestamp: 1709599607 Timestamp [UCT]: 2024-03-05 00:46:47 Age [y:d:h:m:s]: 01:260:01:59:33
Block: 971343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444606 RingCT/type: yes/0
Extra: 019bc1530781957839ae4313af4a742a3d7d9de0628beea3fe10762192df5d750c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db29aefc0f1e5dca53ba2760523b2169cf11aa87346e502d684d4baa19fafd5c 0.600000000000 1431238 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": 971353, "vin": [ { "gen": { "height": 971343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db29aefc0f1e5dca53ba2760523b2169cf11aa87346e502d684d4baa19fafd5c" } } ], "extra": [ 1, 155, 193, 83, 7, 129, 149, 120, 57, 174, 67, 19, 175, 74, 116, 42, 61, 125, 157, 224, 98, 139, 238, 163, 254, 16, 118, 33, 146, 223, 93, 117, 12, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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