Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db597045c3ad7f30c9aba38f9e14891fa98fc9a2fac87b80fc96df9a55c21847

Tx prefix hash: 5a9e56f93cd9eb1a22275e97701672923ce00ee20f49c3aa39530d02edd8234d
Tx public key: 78d73ce24fd6768abb3f8d2228f74ee389036fc3ff4f1760acb13d8db4a52728
Timestamp: 1693314321 Timestamp [UCT]: 2023-08-29 13:05:21 Age [y:d:h:m:s]: 01:185:06:29:43
Block: 836498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393512 RingCT/type: yes/0
Extra: 0178d73ce24fd6768abb3f8d2228f74ee389036fc3ff4f1760acb13d8db4a5272802110000000475e3f0e9000000000000000000

1 output(s) for total of 1.038328932000 dcy

stealth address amount amount idx
00: eb6e7e1366d02a0b50c54cac4b045545e4ef9799e573b981d8aa0abb77c8b369 1.038328932000 1289086 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": 836508, "vin": [ { "gen": { "height": 836498 } } ], "vout": [ { "amount": 1038328932, "target": { "key": "eb6e7e1366d02a0b50c54cac4b045545e4ef9799e573b981d8aa0abb77c8b369" } } ], "extra": [ 1, 120, 215, 60, 226, 79, 214, 118, 138, 187, 63, 141, 34, 40, 247, 78, 227, 137, 3, 111, 195, 255, 79, 23, 96, 172, 177, 61, 141, 180, 165, 39, 40, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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