Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f46f005ad1976ef024a4c4c9f15250ea3d5ba11a139c13b5f4783561b2aa3414

Tx prefix hash: 5f02f3eeeaad178201196ee290ee403c021dd6ec2a7b7f2323ebf51155bf624b
Tx public key: 1488a71012a020e1d67d8ff443f23e22ff854023f49f53f8cf50a4bbe8b62984
Timestamp: 1732193874 Timestamp [UCT]: 2024-11-21 12:57:54 Age [y:d:h:m:s]: 00:146:13:46:40
Block: 1158547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104581 RingCT/type: yes/0
Extra: 011488a71012a020e1d67d8ff443f23e22ff854023f49f53f8cf50a4bbe8b629840211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd2dc52ca1d6b2559d391561454b400181d6834b74b905f4f82f86a73a6f3b9e 0.600000000000 1644176 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": 1158557, "vin": [ { "gen": { "height": 1158547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd2dc52ca1d6b2559d391561454b400181d6834b74b905f4f82f86a73a6f3b9e" } } ], "extra": [ 1, 20, 136, 167, 16, 18, 160, 32, 225, 214, 125, 143, 244, 67, 242, 62, 34, 255, 133, 64, 35, 244, 159, 83, 248, 207, 80, 164, 187, 232, 182, 41, 132, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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