Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c47a43b58b3b95cac200fbed018f4ae5dfa8e2d5c858a1b81ab40bbee402d84

Tx prefix hash: 603ff38ab890a43c14ce375b97045b9ce438d2d02ee6c1d4c515cc391ede057f
Tx public key: b83fe0ced86752534fe0e2b74adbc46bf8f1e44e881d0a2ac3475bdfcef0ab81
Timestamp: 1672792361 Timestamp [UCT]: 2023-01-04 00:32:41 Age [y:d:h:m:s]: 02:333:07:29:36
Block: 667046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 757654 RingCT/type: yes/0
Extra: 01b83fe0ced86752534fe0e2b74adbc46bf8f1e44e881d0a2ac3475bdfcef0ab8102110000000333af99f4000000000000000000

1 output(s) for total of 3.782680491000 dcy

stealth address amount amount idx
00: a39d14101edb28d23b416443264c5b646b7604b3bc9269fcb4f0b8dca935c95b 3.782680491000 1108209 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": 667056, "vin": [ { "gen": { "height": 667046 } } ], "vout": [ { "amount": 3782680491, "target": { "key": "a39d14101edb28d23b416443264c5b646b7604b3bc9269fcb4f0b8dca935c95b" } } ], "extra": [ 1, 184, 63, 224, 206, 216, 103, 82, 83, 79, 224, 226, 183, 74, 219, 196, 107, 248, 241, 228, 78, 136, 29, 10, 42, 195, 71, 91, 223, 206, 240, 171, 129, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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