Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c32dad4ecbb4c0429389d0d204d5b4ffc267cbcf08405f79fb8e9b138f767b87

Tx prefix hash: c14ab855f621470dbecd37b82c3e6c3ae7c3ad6bd3750bf37eb6138f8d11cf14
Tx public key: fccb96305ae708ebd01d51d15c80309160773d7d4acda1097eac101ef2d6a971
Timestamp: 1578519304 Timestamp [UCT]: 2020-01-08 21:35:04 Age [y:d:h:m:s]: 05:100:11:35:55
Block: 41633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221693 RingCT/type: yes/0
Extra: 01fccb96305ae708ebd01d51d15c80309160773d7d4acda1097eac101ef2d6a97102110000004117786bcf000000000000000000

1 output(s) for total of 446.738553391000 dcy

stealth address amount amount idx
00: 4a1bb5d441b18114d5851b4b4722e0e9548a0e4110ea19ee3681c9065342e98a 446.738553391000 74327 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": 41643, "vin": [ { "gen": { "height": 41633 } } ], "vout": [ { "amount": 446738553391, "target": { "key": "4a1bb5d441b18114d5851b4b4722e0e9548a0e4110ea19ee3681c9065342e98a" } } ], "extra": [ 1, 252, 203, 150, 48, 90, 231, 8, 235, 208, 29, 81, 209, 92, 128, 48, 145, 96, 119, 61, 125, 74, 205, 161, 9, 126, 172, 16, 30, 242, 214, 169, 113, 2, 17, 0, 0, 0, 65, 23, 120, 107, 207, 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