Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6ce682e9a3b57776655228f90604d95114a730a633f5c54ae69c6a195491677

Tx prefix hash: 4450846cc5a97562c3f4b3c9c2feb2b1360b81853a9ff9dfe379eb1e7f82b779
Tx public key: 85b4ca58739f0ca3806b88ff100c157b1e92dd8e629690d5fa0e277e8d30f8a8
Timestamp: 1658609911 Timestamp [UCT]: 2022-07-23 20:58:31 Age [y:d:h:m:s]: 02:310:06:53:45
Block: 550211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 743010 RingCT/type: yes/0
Extra: 0185b4ca58739f0ca3806b88ff100c157b1e92dd8e629690d5fa0e277e8d30f8a8021100000004e6d27f9c000000000000000000

1 output(s) for total of 9.224072027000 dcy

stealth address amount amount idx
00: 27c20d341fbc3df7b6946fa2814e8fc46a83d3a9cb8db336ff8eeb768da2ad75 9.224072027000 981672 of 0

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": 550221, "vin": [ { "gen": { "height": 550211 } } ], "vout": [ { "amount": 9224072027, "target": { "key": "27c20d341fbc3df7b6946fa2814e8fc46a83d3a9cb8db336ff8eeb768da2ad75" } } ], "extra": [ 1, 133, 180, 202, 88, 115, 159, 12, 163, 128, 107, 136, 255, 16, 12, 21, 123, 30, 146, 221, 142, 98, 150, 144, 213, 250, 14, 39, 126, 141, 48, 248, 168, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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