Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc480ba850278c7a4f47aa58684a66783d131dc4f91dfecde3a77d0e9a8e0cb3

Tx prefix hash: 8d7138a0670db62d867fc6d4b5e1b4ef48df730cf8fe70955218479f3167be37
Tx public key: 6729f0e7dcb86f8b3390f121ce334d066c5d0785d82a41fb3bd4625178b6157f
Timestamp: 1713066002 Timestamp [UCT]: 2024-04-14 03:40:02 Age [y:d:h:m:s]: 00:320:23:16:19
Block: 1000050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229454 RingCT/type: yes/0
Extra: 016729f0e7dcb86f8b3390f121ce334d066c5d0785d82a41fb3bd4625178b6157f02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ab841fabf0269c13e09a40ac4ac58d398e385a1e763d5e6729e1754df137b16 0.600000000000 1460540 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": 1000060, "vin": [ { "gen": { "height": 1000050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ab841fabf0269c13e09a40ac4ac58d398e385a1e763d5e6729e1754df137b16" } } ], "extra": [ 1, 103, 41, 240, 231, 220, 184, 111, 139, 51, 144, 241, 33, 206, 51, 77, 6, 108, 93, 7, 133, 216, 42, 65, 251, 59, 212, 98, 81, 120, 182, 21, 127, 2, 17, 0, 0, 0, 6, 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