Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdd749e695a2ba2b0a41568bcf463d77cc55dd5eda2105f089a94c9c09b9808e

Tx prefix hash: 0d64aa1a300c818afdd15c17b9a003364e4eacb0b13c88f75ebf9f69ec5af80a
Tx public key: 046f90b6eb9f613bdb8aa9008c77f7bfd378e5d3b131734800e57324383fafc5
Timestamp: 1730065329 Timestamp [UCT]: 2024-10-27 21:42:09 Age [y:d:h:m:s]: 00:086:12:17:06
Block: 1140957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61816 RingCT/type: yes/0
Extra: 01046f90b6eb9f613bdb8aa9008c77f7bfd378e5d3b131734800e57324383fafc5021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2be55adfb81c7067c54cabf0bd92f10d089812caa97cf876c428766e075e0ae 0.600000000000 1624764 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": 1140967, "vin": [ { "gen": { "height": 1140957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2be55adfb81c7067c54cabf0bd92f10d089812caa97cf876c428766e075e0ae" } } ], "extra": [ 1, 4, 111, 144, 182, 235, 159, 97, 59, 219, 138, 169, 0, 140, 119, 247, 191, 211, 120, 229, 211, 177, 49, 115, 72, 0, 229, 115, 36, 56, 63, 175, 197, 2, 17, 0, 0, 0, 7, 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