Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 336742e72740a7019c69b74ab1e0b3eff62dd4b27d6d2a96e0f7fb4f1b3c4e4f

Tx prefix hash: 9366b34c20cdbf015df03ca166ed8653d956f9e08037dcb434ca6fd4ce0f5d26
Tx public key: dc8cf46fa7316ee84dc54aa7bc415c9f48547ae045449f5b354611a2527f1cd5
Timestamp: 1725481943 Timestamp [UCT]: 2024-09-04 20:32:23 Age [y:d:h:m:s]: 00:140:22:26:34
Block: 1103001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100759 RingCT/type: yes/0
Extra: 01dc8cf46fa7316ee84dc54aa7bc415c9f48547ae045449f5b354611a2527f1cd502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cdd7c4f1fe6b5db76209f5b9104240130379b278c9380315e31fbbd65a8c6c4 0.600000000000 1579662 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": 1103011, "vin": [ { "gen": { "height": 1103001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cdd7c4f1fe6b5db76209f5b9104240130379b278c9380315e31fbbd65a8c6c4" } } ], "extra": [ 1, 220, 140, 244, 111, 167, 49, 110, 232, 77, 197, 74, 167, 188, 65, 92, 159, 72, 84, 122, 224, 69, 68, 159, 91, 53, 70, 17, 162, 82, 127, 28, 213, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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