Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 429cf26c0ca3f06bff9ead13b414cd83c73b7cbe88ebae6d76cfa58b3655ff60

Tx prefix hash: bc82191c8d6bf11bc91ef6d02d248b235edad8f1601ee6d70f787344f79dd599
Tx public key: 251dc8d67685be5fff5402aa59347a31512ce3246b02119ddc9fb88661658153
Timestamp: 1581298079 Timestamp [UCT]: 2020-02-10 01:27:59 Age [y:d:h:m:s]: 04:361:14:19:56
Block: 61730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150293 RingCT/type: yes/0
Extra: 01251dc8d67685be5fff5402aa59347a31512ce3246b02119ddc9fb88661658153021100000011d81c26c0000000000000000000

1 output(s) for total of 383.233707318000 dcy

stealth address amount amount idx
00: 9651a0a3bc8fd670a8fda19d4a65ba2b489e3c4888d5af73b3fb1c68bfe95425 383.233707318000 113825 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": 61740, "vin": [ { "gen": { "height": 61730 } } ], "vout": [ { "amount": 383233707318, "target": { "key": "9651a0a3bc8fd670a8fda19d4a65ba2b489e3c4888d5af73b3fb1c68bfe95425" } } ], "extra": [ 1, 37, 29, 200, 214, 118, 133, 190, 95, 255, 84, 2, 170, 89, 52, 122, 49, 81, 44, 227, 36, 107, 2, 17, 157, 220, 159, 184, 134, 97, 101, 129, 83, 2, 17, 0, 0, 0, 17, 216, 28, 38, 192, 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