Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de6bcf3ac88ac35d4e737404e119e685ba37494c963f114520c49d9ff8ae5191

Tx prefix hash: ba0314a1b57651f816b9e2ef61e6aa6ba480c26880166a381ed2924a6d0a0893
Tx public key: f85983e93eb05dea387e6f4c620037f6cee0f2292e7cd14227fafb22e30d8cb3
Timestamp: 1705369065 Timestamp [UCT]: 2024-01-16 01:37:45 Age [y:d:h:m:s]: 01:093:04:20:23
Block: 936230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327717 RingCT/type: yes/0
Extra: 01f85983e93eb05dea387e6f4c620037f6cee0f2292e7cd14227fafb22e30d8cb302110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c3f5917494f4b2729882ffd9351f4be6ee0f0d1d9d04b89179264b196b3c446 0.600000000000 1394254 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": 936240, "vin": [ { "gen": { "height": 936230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c3f5917494f4b2729882ffd9351f4be6ee0f0d1d9d04b89179264b196b3c446" } } ], "extra": [ 1, 248, 89, 131, 233, 62, 176, 93, 234, 56, 126, 111, 76, 98, 0, 55, 246, 206, 224, 242, 41, 46, 124, 209, 66, 39, 250, 251, 34, 227, 13, 140, 179, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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