Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc538f0d3f76cc052c21790333d13635b55e795ab66b93cdf011cc066657a16c

Tx prefix hash: cc848a81da0738f625828d44f073659935090b65d9d494da315f608b5bf2eae7
Tx public key: cd3a3cb5807b3b9bf0b13d9094ad90d098aa40a9d5b30ce829878703d4273aff
Timestamp: 1729427413 Timestamp [UCT]: 2024-10-20 12:30:13 Age [y:d:h:m:s]: 00:144:21:31:04
Block: 1135707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103343 RingCT/type: yes/0
Extra: 01cd3a3cb5807b3b9bf0b13d9094ad90d098aa40a9d5b30ce829878703d4273aff0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c301e53250277c143db2e2db5b0a3ccf3bf7d87794599c6dbf59786e5b7bbf0 0.600000000000 1619046 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": 1135717, "vin": [ { "gen": { "height": 1135707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c301e53250277c143db2e2db5b0a3ccf3bf7d87794599c6dbf59786e5b7bbf0" } } ], "extra": [ 1, 205, 58, 60, 181, 128, 123, 59, 155, 240, 177, 61, 144, 148, 173, 144, 208, 152, 170, 64, 169, 213, 179, 12, 232, 41, 135, 135, 3, 212, 39, 58, 255, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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