Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c7967bf2bfb307a19f80e211946a914fbea69c5f7d78e2a780c2864f411e387

Tx prefix hash: 029e1071fa5c66719748d72f3c8f6ec21da3ee09c98ba8e8e648ea3babee1b63
Tx public key: 0b1157f25b60989694c3c1d6e9ca70de1aac1c1b97175e75fd359d113c43d8e9
Timestamp: 1706683945 Timestamp [UCT]: 2024-01-31 06:52:25 Age [y:d:h:m:s]: 01:133:05:25:48
Block: 947139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356300 RingCT/type: yes/0
Extra: 010b1157f25b60989694c3c1d6e9ca70de1aac1c1b97175e75fd359d113c43d8e90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5e2a2865a5b1dfc4cd4bcb649156a73e0d3ccc560a16249baea395d3ce6b5e4 0.600000000000 1405487 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": 947149, "vin": [ { "gen": { "height": 947139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5e2a2865a5b1dfc4cd4bcb649156a73e0d3ccc560a16249baea395d3ce6b5e4" } } ], "extra": [ 1, 11, 17, 87, 242, 91, 96, 152, 150, 148, 195, 193, 214, 233, 202, 112, 222, 26, 172, 28, 27, 151, 23, 94, 117, 253, 53, 157, 17, 60, 67, 216, 233, 2, 17, 0, 0, 0, 1, 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