Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 388bd8bce02d00341623913eb187b73d7e3b14946dc78603db3ae10851f5ebe7

Tx prefix hash: e7fdfc0a7946037f93373e7989460c0438d80549f2822e27b65b40ac05724118
Tx public key: 01d8ad46cdc8ad213e730524ff7dc2d0affcff0c6c42d8722f2682a3cf454fb3
Timestamp: 1745830728 Timestamp [UCT]: 2025-04-28 08:58:48 Age [y:d:h:m:s]: 00:207:06:04:38
Block: 1271191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145829 RingCT/type: yes/0
Extra: 0101d8ad46cdc8ad213e730524ff7dc2d0affcff0c6c42d8722f2682a3cf454fb30211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2705ccfdf86756463602ada85824cb3b68b4bd45c18f267caa0f8af393a8f7b8 0.600000000000 1758446 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": 1271201, "vin": [ { "gen": { "height": 1271191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2705ccfdf86756463602ada85824cb3b68b4bd45c18f267caa0f8af393a8f7b8" } } ], "extra": [ 1, 1, 216, 173, 70, 205, 200, 173, 33, 62, 115, 5, 36, 255, 125, 194, 208, 175, 252, 255, 12, 108, 66, 216, 114, 47, 38, 130, 163, 207, 69, 79, 179, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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