Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd31943881a189041521382d0b80ecb8ab7dd79b29ea0318c0070b83e0b11596

Tx prefix hash: 418f51a0ba5995bb868167cdf31181a3b8624ff6cda898b49a19a370de143361
Tx public key: 47fc073dbd7bf5b4ce1146d0c2a192cd379a750bf5667e8f6d0e8a88f510b8bf
Timestamp: 1715364350 Timestamp [UCT]: 2024-05-10 18:05:50 Age [y:d:h:m:s]: 01:183:09:27:24
Block: 1019125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389686 RingCT/type: yes/0
Extra: 0147fc073dbd7bf5b4ce1146d0c2a192cd379a750bf5667e8f6d0e8a88f510b8bf021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fbb8813c0f7d3069254621c6f58af3f424af6bf980059ffa70734ccbb8d3da3 0.600000000000 1483012 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": 1019135, "vin": [ { "gen": { "height": 1019125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fbb8813c0f7d3069254621c6f58af3f424af6bf980059ffa70734ccbb8d3da3" } } ], "extra": [ 1, 71, 252, 7, 61, 189, 123, 245, 180, 206, 17, 70, 208, 194, 161, 146, 205, 55, 154, 117, 11, 245, 102, 126, 143, 109, 14, 138, 136, 245, 16, 184, 191, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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