Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d370e03071f1b297c2f667b8674c09c9426d8dc979e845fd507750a2c073eb1d

Tx prefix hash: fab179c4b372feebe3919f501f3f562878b8a67eca80f3962eafc4fca939c029
Tx public key: 3e0e62ea1592e69a94e7ba00a4780399bd3df512e0e58161af05d0301530a361
Timestamp: 1713934736 Timestamp [UCT]: 2024-04-24 04:58:56 Age [y:d:h:m:s]: 01:193:20:19:43
Block: 1007270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397183 RingCT/type: yes/0
Extra: 013e0e62ea1592e69a94e7ba00a4780399bd3df512e0e58161af05d0301530a3610211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f516527cdbd7ab9cf3f65e4301db9bfc94899ba00c81b6eb28b9dfeec8fafb2 0.600000000000 1468556 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": 1007280, "vin": [ { "gen": { "height": 1007270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f516527cdbd7ab9cf3f65e4301db9bfc94899ba00c81b6eb28b9dfeec8fafb2" } } ], "extra": [ 1, 62, 14, 98, 234, 21, 146, 230, 154, 148, 231, 186, 0, 164, 120, 3, 153, 189, 61, 245, 18, 224, 229, 129, 97, 175, 5, 208, 48, 21, 48, 163, 97, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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