Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342f7a30e3bdd5e4df3be8f6d237d4fc9b933d83f86c2f79c435b41d0e8c2d49

Tx prefix hash: 636f8e124b0e1ec534805689882f926aaa70a28d321d595f235346abda51b8d9
Tx public key: 0c90c118c7f94e1db15be5c60fed036be303eab36c15eef220327186940cbdfa
Timestamp: 1715029925 Timestamp [UCT]: 2024-05-06 21:12:05 Age [y:d:h:m:s]: 00:201:18:39:20
Block: 1016363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144432 RingCT/type: yes/0
Extra: 010c90c118c7f94e1db15be5c60fed036be303eab36c15eef220327186940cbdfa0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: a84a5f559cc4404f83b990b81c4b8fb8fefb8184fe52887d619fff67e23a5f7c 0.600010000000 1479918 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": 1016373, "vin": [ { "gen": { "height": 1016363 } } ], "vout": [ { "amount": 600010000, "target": { "key": "a84a5f559cc4404f83b990b81c4b8fb8fefb8184fe52887d619fff67e23a5f7c" } } ], "extra": [ 1, 12, 144, 193, 24, 199, 249, 78, 29, 177, 91, 229, 198, 15, 237, 3, 107, 227, 3, 234, 179, 108, 21, 238, 242, 32, 50, 113, 134, 148, 12, 189, 250, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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