Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 448e2c4d18b42dc4a6750f2497a8194237f79120d90005f76976562b3aa1b746

Tx prefix hash: 47fa705a78cce44046564e708eb7fd4b62a7c58e1dd4a14af10321ebae1d78c0
Tx public key: 0e9259a5e0d8a00a64128711fccdaa5d0a32f53c760ff83aef40cd4d05140c4d
Timestamp: 1697763259 Timestamp [UCT]: 2023-10-20 00:54:19 Age [y:d:h:m:s]: 01:166:19:31:53
Block: 873410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380229 RingCT/type: yes/0
Extra: 010e9259a5e0d8a00a64128711fccdaa5d0a32f53c760ff83aef40cd4d05140c4d0211000000064b8f5122000000000000000000

1 output(s) for total of 0.783483983000 dcy

stealth address amount amount idx
00: dea06c5da0cf0253801884674af672877b4138a1ed5110817c115a15dcde195e 0.783483983000 1328556 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": 873420, "vin": [ { "gen": { "height": 873410 } } ], "vout": [ { "amount": 783483983, "target": { "key": "dea06c5da0cf0253801884674af672877b4138a1ed5110817c115a15dcde195e" } } ], "extra": [ 1, 14, 146, 89, 165, 224, 216, 160, 10, 100, 18, 135, 17, 252, 205, 170, 93, 10, 50, 245, 60, 118, 15, 248, 58, 239, 64, 205, 77, 5, 20, 12, 77, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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