Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ba48786dc5548a60deb0fc1aaa9b060c76d0256522b49df19492a0a51d55b27

Tx prefix hash: 463cc1b1def81bf6389c40e85fbf1f1d220461f3cd1cca9e0d920240e5e1e272
Tx public key: 6d1f2a0a96e734129934adc18ce0a92ce34cddc2b1cf8e31b9150cdffc7710ea
Timestamp: 1718995518 Timestamp [UCT]: 2024-06-21 18:45:18 Age [y:d:h:m:s]: 00:270:16:46:24
Block: 1049202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193470 RingCT/type: yes/0
Extra: 016d1f2a0a96e734129934adc18ce0a92ce34cddc2b1cf8e31b9150cdffc7710ea02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e978e225cef60f5b0478ceddfce5e166465d8db9ee12224aa911bfb56f14da9 0.600000000000 1519299 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": 1049212, "vin": [ { "gen": { "height": 1049202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e978e225cef60f5b0478ceddfce5e166465d8db9ee12224aa911bfb56f14da9" } } ], "extra": [ 1, 109, 31, 42, 10, 150, 231, 52, 18, 153, 52, 173, 193, 140, 224, 169, 44, 227, 76, 221, 194, 177, 207, 142, 49, 185, 21, 12, 223, 252, 119, 16, 234, 2, 17, 0, 0, 0, 4, 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