Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49c980d5f75799916e2c92a4661017b69e2b01ec38c483bfbeec8eb3539697b1

Tx prefix hash: 71b788f7843d79a94bf4b9d989573cbe451fd8abba78c7c9cc6ffb6405dc4fe4
Tx public key: 0d8765455be60ceb7280f2c932a89df69adef8186e02ee9df00f5f121613f77a
Timestamp: 1728946368 Timestamp [UCT]: 2024-10-14 22:52:48 Age [y:d:h:m:s]: 01:025:04:03:20
Block: 1131729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276343 RingCT/type: yes/0
Extra: 010d8765455be60ceb7280f2c932a89df69adef8186e02ee9df00f5f121613f77a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca44f0e33ab428adfff589739497882d88fbe833e84c8085a0d8a5ece813df94 0.600000000000 1614634 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": 1131739, "vin": [ { "gen": { "height": 1131729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca44f0e33ab428adfff589739497882d88fbe833e84c8085a0d8a5ece813df94" } } ], "extra": [ 1, 13, 135, 101, 69, 91, 230, 12, 235, 114, 128, 242, 201, 50, 168, 157, 246, 154, 222, 248, 24, 110, 2, 238, 157, 240, 15, 95, 18, 22, 19, 247, 122, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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