Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64e29fa90e3e81093ad95a7d98468187dca820e533d9d4e54016dd68fb862c6f

Tx prefix hash: ab842fd83d16577ea470782a911c2077dbf690fcc5f5a1ecaa734eccc2b1a02c
Tx public key: 324088aeea120c7350f4a8fd8581a0a073bf5dd6cbef82955142621c9b3bad90
Timestamp: 1730443972 Timestamp [UCT]: 2024-11-01 06:52:52 Age [y:d:h:m:s]: 00:022:23:30:35
Block: 1144061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16436 RingCT/type: yes/0
Extra: 01324088aeea120c7350f4a8fd8581a0a073bf5dd6cbef82955142621c9b3bad90021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa77a48eb65b70ddaad6360951c57bf593ec83bf1d3ef7f3cba3c70c71d175c4 0.600000000000 1628140 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": 1144071, "vin": [ { "gen": { "height": 1144061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa77a48eb65b70ddaad6360951c57bf593ec83bf1d3ef7f3cba3c70c71d175c4" } } ], "extra": [ 1, 50, 64, 136, 174, 234, 18, 12, 115, 80, 244, 168, 253, 133, 129, 160, 160, 115, 191, 93, 214, 203, 239, 130, 149, 81, 66, 98, 28, 155, 59, 173, 144, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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