Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b947b161bccf855c594193c171a396d2d6beb99f45bfb90e9641e935ee7e32e

Tx prefix hash: cb58370c61db59e3d4b16106022e4c4ca08fa965eb824f4ac04ece2207a935b0
Tx public key: 3b46277695904372d07bfd9a7982bf25580c8e7c4c955c0b22f1a281a8460e93
Timestamp: 1709275530 Timestamp [UCT]: 2024-03-01 06:45:30 Age [y:d:h:m:s]: 00:342:01:27:21
Block: 968657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244569 RingCT/type: yes/0
Extra: 013b46277695904372d07bfd9a7982bf25580c8e7c4c955c0b22f1a281a8460e930211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba16ff2fe358bc9d3c0a57fd4ca6bd90dfd7bc55456575c32ccfa221d97c9169 0.600000000000 1428474 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": 968667, "vin": [ { "gen": { "height": 968657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba16ff2fe358bc9d3c0a57fd4ca6bd90dfd7bc55456575c32ccfa221d97c9169" } } ], "extra": [ 1, 59, 70, 39, 118, 149, 144, 67, 114, 208, 123, 253, 154, 121, 130, 191, 37, 88, 12, 142, 124, 76, 149, 92, 11, 34, 241, 162, 129, 168, 70, 14, 147, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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