Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fbe10afea9c85a87cf1707d63814d1ddf3c22f051645f6f2529ac142ad4125a

Tx prefix hash: 496b08620d1463ad90cc8337359fcaae5977c2e75168e86d6798eb8deb5e7361
Tx public key: c584a119b9c58f956ab8cebc90a24632e8ec037f1931fcc50f9a62f9b4a8b704
Timestamp: 1735873801 Timestamp [UCT]: 2025-01-03 03:10:01 Age [y:d:h:m:s]: 00:307:09:35:34
Block: 1189025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217181 RingCT/type: yes/0
Extra: 01c584a119b9c58f956ab8cebc90a24632e8ec037f1931fcc50f9a62f9b4a8b704021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b31ebd92d763196a7f37e102d9103003bffa949a28c49770eabfca4c35fb1f7e 0.600000000000 1675530 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": 1189035, "vin": [ { "gen": { "height": 1189025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b31ebd92d763196a7f37e102d9103003bffa949a28c49770eabfca4c35fb1f7e" } } ], "extra": [ 1, 197, 132, 161, 25, 185, 197, 143, 149, 106, 184, 206, 188, 144, 162, 70, 50, 232, 236, 3, 127, 25, 49, 252, 197, 15, 154, 98, 249, 180, 168, 183, 4, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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