Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 149c0d59ca5a88bde725276fb7574e8a5c65944002fbcfacd72f29f70aa4532d

Tx prefix hash: 9effda1210ff51357ebfd3666fe5dec69f7669757ca52f3aa47e758d95cfb361
Tx public key: 288ac52b51272db712ab9fbfe927c4fe94fb4d36421b5a4a9f0edafc0fd900bf
Timestamp: 1732207374 Timestamp [UCT]: 2024-11-21 16:42:54 Age [y:d:h:m:s]: 00:139:10:51:40
Block: 1158664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99488 RingCT/type: yes/0
Extra: 01288ac52b51272db712ab9fbfe927c4fe94fb4d36421b5a4a9f0edafc0fd900bf0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b15c3617a445dc015cf68ab8b405b60704981740631c1a4eaa1a7014847c3389 0.600000000000 1644293 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": 1158674, "vin": [ { "gen": { "height": 1158664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b15c3617a445dc015cf68ab8b405b60704981740631c1a4eaa1a7014847c3389" } } ], "extra": [ 1, 40, 138, 197, 43, 81, 39, 45, 183, 18, 171, 159, 191, 233, 39, 196, 254, 148, 251, 77, 54, 66, 27, 90, 74, 159, 14, 218, 252, 15, 217, 0, 191, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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