Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0ad28c551ae7de612fc89996a2042198d499a5dcc3ed9e66d3267565a09e68b

Tx prefix hash: 4b48647cb14d56634d7d93ed7d39162f8a1279fdacffcbe382a74477bf64af41
Tx public key: e9eacfd638b58aa2ee87ccc327ee94054b4fd75d853d080e7fa471445fbeb071
Timestamp: 1732253195 Timestamp [UCT]: 2024-11-22 05:26:35 Age [y:d:h:m:s]: 00:001:23:58:51
Block: 1159040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1435 RingCT/type: yes/0
Extra: 01e9eacfd638b58aa2ee87ccc327ee94054b4fd75d853d080e7fa471445fbeb071021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d795f4e6081c2e5cd724c4489436e7560f47dc87fee3e309f23834638ca818c 0.600000000000 1644671 of 15

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": 1159050, "vin": [ { "gen": { "height": 1159040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d795f4e6081c2e5cd724c4489436e7560f47dc87fee3e309f23834638ca818c" } } ], "extra": [ 1, 233, 234, 207, 214, 56, 181, 138, 162, 238, 135, 204, 195, 39, 238, 148, 5, 75, 79, 215, 93, 133, 61, 8, 14, 127, 164, 113, 68, 95, 190, 176, 113, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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