Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe4d1e4ee00d6c3787178d62953b6208b4e6a7716c9a048fc86ddaad60e7419

Tx prefix hash: 4704705d0544dd8a2e092ffcce98244bd857262539e0c5d591a397b1893f9486
Tx public key: 2e1c12467abae12de18b625e14fa67ca9ca94c6a60162bca33eea4eb2a18c0fd
Timestamp: 1699705509 Timestamp [UCT]: 2023-11-11 12:25:09 Age [y:d:h:m:s]: 01:139:05:32:31
Block: 889310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360689 RingCT/type: yes/0
Extra: 012e1c12467abae12de18b625e14fa67ca9ca94c6a60162bca33eea4eb2a18c0fd02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.693979751000 dcy

stealth address amount amount idx
00: 9f00a37ddfe31e9d1e935894fd6c6e3e18a57a7e6d3e4f7f15f069df6e2442f0 0.693979751000 1345297 of 0

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": 889320, "vin": [ { "gen": { "height": 889310 } } ], "vout": [ { "amount": 693979751, "target": { "key": "9f00a37ddfe31e9d1e935894fd6c6e3e18a57a7e6d3e4f7f15f069df6e2442f0" } } ], "extra": [ 1, 46, 28, 18, 70, 122, 186, 225, 45, 225, 139, 98, 94, 20, 250, 103, 202, 156, 169, 76, 106, 96, 22, 43, 202, 51, 238, 164, 235, 42, 24, 192, 253, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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