Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fb9b32c2d3d29d01d1c8da261ac9061dd56975b79ce6b7c218e4181304d7d9d

Tx prefix hash: 03018c54b037595f2c0c3127de901cd7f5e9fe3ae8f0f7629efe800bd729cb7d
Tx public key: c59666fc82fb83f6c12887f8310e213d3bb79c88480b145f0a30941dc576079e
Timestamp: 1578868638 Timestamp [UCT]: 2020-01-12 22:37:18 Age [y:d:h:m:s]: 04:318:11:00:41
Block: 44228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117087 RingCT/type: yes/0
Extra: 01c59666fc82fb83f6c12887f8310e213d3bb79c88480b145f0a30941dc576079e0211000000158a2ee0d9000000000000000000

1 output(s) for total of 437.980845384000 dcy

stealth address amount amount idx
00: a76b9139dbdc7bd3d968d96dc9fbb0ddaa259325d840f1fa80b87d7e1cfb12af 437.980845384000 80418 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": 44238, "vin": [ { "gen": { "height": 44228 } } ], "vout": [ { "amount": 437980845384, "target": { "key": "a76b9139dbdc7bd3d968d96dc9fbb0ddaa259325d840f1fa80b87d7e1cfb12af" } } ], "extra": [ 1, 197, 150, 102, 252, 130, 251, 131, 246, 193, 40, 135, 248, 49, 14, 33, 61, 59, 183, 156, 136, 72, 11, 20, 95, 10, 48, 148, 29, 197, 118, 7, 158, 2, 17, 0, 0, 0, 21, 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