Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff91051d6a64094177d965e707f1a2cd602ecf9a7391898e731173d8ca291bd6

Tx prefix hash: 24663f3c2b704592fc3cca69e8d9da27e5160e8a43f69560d7e029e8a66504be
Tx public key: e3923a7e5a9e1029e880afb32a71ae7820fbdb784e57ca781bffe7f90fcdeafe
Timestamp: 1704814361 Timestamp [UCT]: 2024-01-09 15:32:41 Age [y:d:h:m:s]: 01:304:00:44:52
Block: 931649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476113 RingCT/type: yes/0
Extra: 01e3923a7e5a9e1029e880afb32a71ae7820fbdb784e57ca781bffe7f90fcdeafe02110000000f52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41a0962b6f3a03b311eb1beafc36c3d43af7edab4cbfb61a78679af8395dae37 0.600000000000 1389553 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": 931659, "vin": [ { "gen": { "height": 931649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41a0962b6f3a03b311eb1beafc36c3d43af7edab4cbfb61a78679af8395dae37" } } ], "extra": [ 1, 227, 146, 58, 126, 90, 158, 16, 41, 232, 128, 175, 179, 42, 113, 174, 120, 32, 251, 219, 120, 78, 87, 202, 120, 27, 255, 231, 249, 15, 205, 234, 254, 2, 17, 0, 0, 0, 15, 82, 212, 126, 148, 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