Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90f2e1f92609c8890741ad148ebf77e182bfa7e3b5cbfc4b23711b4bf577cd47

Tx prefix hash: 04729a30770ba128aa2be97349e2541ab4411b1868b86236331b373b043807c5
Tx public key: 0eef55d531252b139c1a80f8902cf3f7b5e903076e874c9ca1393611fa8e655a
Timestamp: 1580120234 Timestamp [UCT]: 2020-01-27 10:17:14 Age [y:d:h:m:s]: 05:256:03:57:46
Block: 54009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1331489 RingCT/type: yes/0
Extra: 010eef55d531252b139c1a80f8902cf3f7b5e903076e874c9ca1393611fa8e655a02110000003649b77a3d000000000000000000

1 output(s) for total of 406.486933616000 dcy

stealth address amount amount idx
00: b9b3144905081f2d183e91096fc3d251f6ea3a73dde1cecf177222131f1dc1e4 406.486933616000 100027 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": 54019, "vin": [ { "gen": { "height": 54009 } } ], "vout": [ { "amount": 406486933616, "target": { "key": "b9b3144905081f2d183e91096fc3d251f6ea3a73dde1cecf177222131f1dc1e4" } } ], "extra": [ 1, 14, 239, 85, 213, 49, 37, 43, 19, 156, 26, 128, 248, 144, 44, 243, 247, 181, 233, 3, 7, 110, 135, 76, 156, 161, 57, 54, 17, 250, 142, 101, 90, 2, 17, 0, 0, 0, 54, 73, 183, 122, 61, 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