Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d457caac9b586b5a52b48b974b2d5bbe2ff7944bac7d9540fd3f100f0100431

Tx prefix hash: 2cb24a18641ec91a63e78041b1853a2f086f1e6de4ad462f6982c9693fc3f744
Tx public key: 1565167a7a1247391c1d20f9a5a1e740441bcd712e39df5c2af03f65e2354a23
Timestamp: 1737312350 Timestamp [UCT]: 2025-01-19 18:45:50 Age [y:d:h:m:s]: 00:349:19:06:59
Block: 1200907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247603 RingCT/type: yes/0
Extra: 011565167a7a1247391c1d20f9a5a1e740441bcd712e39df5c2af03f65e2354a2302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b93aaf6aa2bb2109b34d187000fee46fe34a39edb4cd64593353e6d8e1393b45 0.600000000000 1687554 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": 1200917, "vin": [ { "gen": { "height": 1200907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b93aaf6aa2bb2109b34d187000fee46fe34a39edb4cd64593353e6d8e1393b45" } } ], "extra": [ 1, 21, 101, 22, 122, 122, 18, 71, 57, 28, 29, 32, 249, 165, 161, 231, 64, 68, 27, 205, 113, 46, 57, 223, 92, 42, 240, 63, 101, 226, 53, 74, 35, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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