Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a5e3bf211594caa00a16b8403c172b83aef5297bf86292933d5d58b1fedad27

Tx prefix hash: 8a530e1934cefe7c0080afbcaa168a1855cb32b5c9986fc5f91f5d4f6f46d048
Tx public key: 36a99740b3a8c2be34360407e3b4f853a05333f0776565200c193ba417686301
Timestamp: 1683629396 Timestamp [UCT]: 2023-05-09 10:49:56 Age [y:d:h:m:s]: 01:247:17:54:37
Block: 756290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438503 RingCT/type: yes/0
Extra: 0136a99740b3a8c2be34360407e3b4f853a05333f0776565200c193ba417686301021100000005e7ace25d000000000000000000

1 output(s) for total of 1.914685609000 dcy

stealth address amount amount idx
00: dccc8d0be8f734a6c6c2b29584aab7af07e9856a91c6421993c47276c95f7e3b 1.914685609000 1204649 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": 756300, "vin": [ { "gen": { "height": 756290 } } ], "vout": [ { "amount": 1914685609, "target": { "key": "dccc8d0be8f734a6c6c2b29584aab7af07e9856a91c6421993c47276c95f7e3b" } } ], "extra": [ 1, 54, 169, 151, 64, 179, 168, 194, 190, 52, 54, 4, 7, 227, 180, 248, 83, 160, 83, 51, 240, 119, 101, 101, 32, 12, 25, 59, 164, 23, 104, 99, 1, 2, 17, 0, 0, 0, 5, 231, 172, 226, 93, 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