Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f634086e20738b313a5a1563d892146cd3fc6270e945f9a08afb8df8d98556a

Tx prefix hash: 9d659b31e8fc5c3e4a88a16ea9adc7e653ada7e7c554dc27724bd1864bd3cb09
Tx public key: 168b9193d783210d581f67eccd9088eab6e032cd363aa58b29456f1551e5c569
Timestamp: 1658795847 Timestamp [UCT]: 2022-07-26 00:37:27 Age [y:d:h:m:s]: 02:160:18:35:54
Block: 551768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636301 RingCT/type: yes/0
Extra: 01168b9193d783210d581f67eccd9088eab6e032cd363aa58b29456f1551e5c5690211000000176570b1ef000000000000000000

1 output(s) for total of 9.115147398000 dcy

stealth address amount amount idx
00: 33f5cfa758f0ec85df8d98ba1bba7c56b043a1a3a26c738e40fb86badf45f467 9.115147398000 983412 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": 551778, "vin": [ { "gen": { "height": 551768 } } ], "vout": [ { "amount": 9115147398, "target": { "key": "33f5cfa758f0ec85df8d98ba1bba7c56b043a1a3a26c738e40fb86badf45f467" } } ], "extra": [ 1, 22, 139, 145, 147, 215, 131, 33, 13, 88, 31, 103, 236, 205, 144, 136, 234, 182, 224, 50, 205, 54, 58, 165, 139, 41, 69, 111, 21, 81, 229, 197, 105, 2, 17, 0, 0, 0, 23, 101, 112, 177, 239, 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