Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 094198889cf18e49385bc8e2c43bc2a0a1b12ebead0ce028baa5501eb60feb1a

Tx prefix hash: de6ab1b1165c8cb3877c0cce9f71d0824e0ac18b5b87bd37a8d8dc4fd65e1bf4
Tx public key: 4c9c8d071b4609f4f5518406a224f1cdbb72fde340b5bd7b76c0fbdc2bfcce6d
Timestamp: 1728844377 Timestamp [UCT]: 2024-10-13 18:32:57 Age [y:d:h:m:s]: 00:219:22:53:26
Block: 1130881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157028 RingCT/type: yes/0
Extra: 014c9c8d071b4609f4f5518406a224f1cdbb72fde340b5bd7b76c0fbdc2bfcce6d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b31c73fed4d2e696284707c3b6974c5c04a7dd2c56cd40c89e0497a39fde68a 0.600000000000 1613762 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": 1130891, "vin": [ { "gen": { "height": 1130881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b31c73fed4d2e696284707c3b6974c5c04a7dd2c56cd40c89e0497a39fde68a" } } ], "extra": [ 1, 76, 156, 141, 7, 27, 70, 9, 244, 245, 81, 132, 6, 162, 36, 241, 205, 187, 114, 253, 227, 64, 181, 189, 123, 118, 192, 251, 220, 43, 252, 206, 109, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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