Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37303c55c9e894fed1bec4b9d1aebf0d1b8e8cc3b7e275fa79590299c5e7e9f4

Tx prefix hash: 8cfa8e6bdb282acf771c72bbdb5d5c2e0126f74ca2aa6ec67284ff18412db7d1
Tx public key: 02b2995a5df686e801731755f76084c85c3f217615c8f13cb041aeb09769751b
Timestamp: 1713704985 Timestamp [UCT]: 2024-04-21 13:09:45 Age [y:d:h:m:s]: 00:309:23:02:26
Block: 1005366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221556 RingCT/type: yes/0
Extra: 0102b2995a5df686e801731755f76084c85c3f217615c8f13cb041aeb09769751b0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27742c8a6ab2d833cdf95219c6f2f9d8ffe89c508d8e98810dc634ae02d04a1b 0.600000000000 1466010 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": 1005376, "vin": [ { "gen": { "height": 1005366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27742c8a6ab2d833cdf95219c6f2f9d8ffe89c508d8e98810dc634ae02d04a1b" } } ], "extra": [ 1, 2, 178, 153, 90, 93, 246, 134, 232, 1, 115, 23, 85, 247, 96, 132, 200, 92, 63, 33, 118, 21, 200, 241, 60, 176, 65, 174, 176, 151, 105, 117, 27, 2, 17, 0, 0, 0, 7, 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