Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ab2f22b0c356194ab6cd5c7dcc452db896eff5c2c9471d754635545150f368d

Tx prefix hash: 495f694a556f689a8317fae20cb249af0a3eedfe103ef812e1f3ae74a773ec4f
Tx public key: 282d4cd7c20eafa41324af7a25863573d58408c55aa4771614407fd5a1fdbbc5
Timestamp: 1630072119 Timestamp [UCT]: 2021-08-27 13:48:39 Age [y:d:h:m:s]: 03:159:05:08:33
Block: 321855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 888110 RingCT/type: yes/0
Extra: 01282d4cd7c20eafa41324af7a25863573d58408c55aa4771614407fd5a1fdbbc502110000002551fa4013000000000000000000

1 output(s) for total of 52.669747350000 dcy

stealth address amount amount idx
00: 6b0196c4b6d6e673d44106cfc40e77d8402b0148f0def916cff63fa9f5c699d2 52.669747350000 668010 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": 321865, "vin": [ { "gen": { "height": 321855 } } ], "vout": [ { "amount": 52669747350, "target": { "key": "6b0196c4b6d6e673d44106cfc40e77d8402b0148f0def916cff63fa9f5c699d2" } } ], "extra": [ 1, 40, 45, 76, 215, 194, 14, 175, 164, 19, 36, 175, 122, 37, 134, 53, 115, 213, 132, 8, 197, 90, 164, 119, 22, 20, 64, 127, 213, 161, 253, 187, 197, 2, 17, 0, 0, 0, 37, 81, 250, 64, 19, 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