Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1200c38aa0ff6b66338416e9521576a69e628da60224c7c4029b3693173bf28

Tx prefix hash: f0f8547d479cc03e217b994a97f0c2dc05e00eea0f97b7548128f37a6004e13d
Tx public key: f6a38f9de6d80f8ae86550e7944dbdea4c7253fdf476aa61bc52ca548f4b42d0
Timestamp: 1573874005 Timestamp [UCT]: 2019-11-16 03:13:25 Age [y:d:h:m:s]: 05:178:20:52:02
Block: 9383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0801 kB
Tx version: 2 No of confirmations: 1271549 RingCT/type: yes/0
Extra: 01f6a38f9de6d80f8ae86550e7944dbdea4c7253fdf476aa61bc52ca548f4b42d0

1 output(s) for total of 571.361691170000 dcy

stealth address amount amount idx
00: 0f17cf473f495685476ca15c0dc37eab365b0a0702fba5b779f5df7c7f2dfbe7 571.361691170000 10394 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": 9393, "vin": [ { "gen": { "height": 9383 } } ], "vout": [ { "amount": 571361691170, "target": { "key": "0f17cf473f495685476ca15c0dc37eab365b0a0702fba5b779f5df7c7f2dfbe7" } } ], "extra": [ 1, 246, 163, 143, 157, 230, 216, 15, 138, 232, 101, 80, 231, 148, 77, 189, 234, 76, 114, 83, 253, 244, 118, 170, 97, 188, 82, 202, 84, 143, 75, 66, 208 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8